This PR delete the contents of the procedural/remote package and comments out the publishing block. I think these interfaces will be helpful in the future, but for now they are dead weight and probably ought to be reimplemented anyway.
Those plan/simresult implementations aren’t very useful right now because they only work with constraints
More work is needed to make an editableplan implementation
It is slowing down the development process for things like external profiles/events
Theresa mentioned a while ago that I probably should have done it in graphql not sql anyway
Verification
I had to delete TimelineRemoteTests.java in the e2e tests, which is kinda useful, but I could bring it back later when I recreate it in graphql.
Documentation
Future work
After procedural constraints is out, I can republish the package and recreate them in graphql.
Description
This PR delete the contents of the procedural/remote package and comments out the publishing block. I think these interfaces will be helpful in the future, but for now they are dead weight and probably ought to be reimplemented anyway.
Verification
I had to delete TimelineRemoteTests.java in the e2e tests, which is kinda useful, but I could bring it back later when I recreate it in graphql.
Documentation
Future work
After procedural constraints is out, I can republish the package and recreate them in graphql.