You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
crystalline doesn't work in Lucky projects, becuse it can't find required classes in migrations. The reason can be that the db/ directory is in the project root, not in the src/ folder.
Also, it doesn't work with macro-generated Lucky classes, like MyModel::DeleteOperation.
The text was updated successfully, but these errors were encountered:
crystalline doesn't work in Lucky projects, becuse it can't find required classes in migrations. The reason can be that the db/ directory is in the project root, not in the src/ folder.
The entry point part of the readme should hopefully cover this - creating a custom .crystalline_main.cr file which requires both folders.
Also, it doesn't work with macro-generated Lucky classes, like MyModel::DeleteOperation.
This is also expected, the only support for macros yet is showing the expansion on hover.
This is also expected, the only support for macros yet is showing the expansion on hover.
But if a class inherits from a macro-generated class, then LSP support stops working inside the class e.g. goto definition, or autocompletion doesn't work, even if the goto target class is not macro-generated.
crystalline
doesn't work in Lucky projects, becuse it can't find required classes in migrations. The reason can be that thedb/
directory is in the project root, not in thesrc/
folder.Also, it doesn't work with macro-generated Lucky classes, like
MyModel::DeleteOperation
.The text was updated successfully, but these errors were encountered: