Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Yaml] Expectation for psi/lexer changes in core plugin #626

Closed
Haehnchen opened this issue Nov 18, 2015 · 22 comments
Closed

[Yaml] Expectation for psi/lexer changes in core plugin #626

Haehnchen opened this issue Nov 18, 2015 · 22 comments

Comments

@Haehnchen
Copy link
Owner

YAML Plugin will get some more love. So some symfony plugin hacks can be removed and pattern need to change.

  • Implement testing for most used Utils to find lexer and psi changes that breaks features
  • Prepare list of most painful workarounds ;)
  • Legacy support possible; need it?
  • ... ?
@rvanlaak
Copy link

rvanlaak commented Feb 1, 2016

Great news about the Yaml plugin 👍 You have an update on the IntelliJ status?

@sidz
Copy link

sidz commented Feb 22, 2016

Hi, when or where can we get smth like alpha or beta version of this plugin for PS 11? Thank you

@Haehnchen
Copy link
Owner Author

not soon; lot of work

@Haehnchen Haehnchen modified the milestone: PhpStorm 2016.1 Mar 13, 2016
@nicwortel
Copy link

Does this mean that we cannot use the plugin with the new PhpStorm 2016.1 yet? Just checking before I upgrade PhpStorm...

@joshuataylor
Copy link

@nicwortel It's not a major update anyway, so you can probably hold off 5. This plugin dictates for example when I update PHPStorm.

@linaori
Copy link

linaori commented Mar 18, 2016

I can't upgrade to the newest phpstorm because of yaml errors. I would offer to help out but my java knowledge is far too poor for this :(

@stof
Copy link
Contributor

stof commented Mar 18, 2016

@Haehnchen do you have any plan for this ? 145.x builds are not the stable version

@Haehnchen
Copy link
Owner Author

having some free time during this week, will try my best

@leusic38
Copy link

Damned I'll work on symfony project next 2 weeks and I updated phpstorm before seeing this bug

@samplenull
Copy link

@leusic38 Download and use previous version for now https://confluence.jetbrains.com/display/PhpStorm/Previous+PhpStorm+Releases

@scaytrase
Copy link

I use to have two versions of PhpStorm in parallel (Major + EAP or Major + new Major). Updating to new PhpStorm major version never goes flawlessly

@ureimers
Copy link

@leusic38 I simply installed PhpStorm 10 again (and let the installer remove 2016 by itself). Took 2 minutes and I'm able to use all plugins.

@Haehnchen I will try to twist my bosses arm to donate you some money. Doing this all by yourself, I have to say I almost feel guilty when I read "having some free time during this week, will try my best". You need to get recompensed for the hours and hours you put into these incredibly time saving plugin(s).

@Haehnchen
Copy link
Owner Author

... done. will test during worktime for missing implementations that not covered by test cases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests