Comments (20)
In GitLab by @manuelma on Jan 25, 2019, 21:18
mentioned in commit 0e05275
from spine-database-api.
In GitLab by @manuelma on Jan 25, 2019, 21:19
This is now implemented and tested.
from spine-database-api.
In GitLab by @manuelma on Jan 25, 2019, 21:19
closed
from spine-database-api.
In GitLab by @manuelma on Jan 31, 2019, 14:45
reopened
from spine-database-api.
In GitLab by @manuelma on Jan 31, 2019, 14:49
Actually we may need to do one more thing. Now I just renamed the table but didn't touch the API, so that clients won't note the difference. But I think we need to homogenize the name everywhere and that means modifying the API and updating the clients as well, toolbox and model. It's a lot of 'search and replace' work, but I think we need to do it. @PvPer
from spine-database-api.
In GitLab by @manuelma on Feb 4, 2019, 20:16
mentioned in commit dd50307
from spine-database-api.
In GitLab by @manuelma on Feb 8, 2019, 17:36
mentioned in commit b7918e8
from spine-database-api.
In GitLab by @manuelma on Feb 8, 2019, 17:43
mentioned in commit 1f1e74c
from spine-database-api.
In GitLab by @manuelma on Feb 8, 2019, 17:46
mentioned in commit c06553f
from spine-database-api.
In GitLab by @manuelma on Feb 19, 2019, 21:06
mentioned in commit 32f5085
from spine-database-api.
In GitLab by @manuelma on Feb 22, 2019, 14:09
mentioned in commit 1b87ca2
from spine-database-api.
In GitLab by @manuelma on May 30, 2019, 19:11
This is still pending. But here's a question: is it ok to just change exported names and adapt our API clients so it works, without caring about the outside world?
I have so far avoided this, by issuing deprecation warnings in methods whose name I want to change (eg. add_parameter
method to add_parameter_definition
)
My plan is to let some time pass and then change the name. But maybe I'm being too conservative.
from spine-database-api.
In GitLab by @jkiviluo on Jun 3, 2019, 12:21
If you do the changes, everybody just needs to update into the latest versions of DB and API at the same time? I think that should be ok still - just let people know in Slack.
from spine-database-api.
In GitLab by @manuelma on Jun 5, 2019, 23:46
mentioned in commit 3a8f95b
from spine-database-api.
In GitLab by @manuelma on Jun 5, 2019, 23:47
mentioned in commit toolbox@8286a6f20ed81a23d4f78726dcc95f9969c73e66
from spine-database-api.
In GitLab by @manuelma on Jun 5, 2019, 23:47
mentioned in commit SpineInterface.jl@3f1981f4771ef462a45196a0ecfd0059cedc18ca
from spine-database-api.
In GitLab by @manuelma on Jun 6, 2019, 00:11
mentioned in commit toolbox@0715e8dfc2c85f27567473b78851219f1be9a88a
from spine-database-api.
In GitLab by @manuelma on Jun 6, 2019, 00:11
mentioned in commit 21ebf5d
from spine-database-api.
In GitLab by @manuelma on Jun 6, 2019, 00:15
mentioned in commit toolbox@c50d97e6d4b3abadefff1e4216ff227375b93739
from spine-database-api.
The tables have been renamed.
from spine-database-api.
Related Issues (20)
- Restablish unique key 'name' for entity_class
- Parameter values as Apache Arrow objects HOT 4
- Can't trust legacy tool/feature/method for compatibility transformations
- Write type information for simple types as well
- Rollback purge HOT 1
- Add Toolbox tests to GitHub actions? HOT 3
- Parameter value format documentation is missing index_name
- Wrong results after changing a filter
- Make sure TempId travel safely across the socket (DB server)
- The tool filter only works with 1 tool activated
- No entity can pass its tool filter when there are multiple `tool_feature_method`s HOT 1
- Fix broken example in parameter_value API documentation
- Guidelines on what to import in __init__.py
- Improve parsing performance by accepting only ISO 8601 time stamps HOT 2
- Check that CHANGELOG.md is up-to-date for 0.8-dev HOT 1
- Compatibility transformation should keep working after the first time HOT 1
- Alternative filter does not filter by entity alternatives
- Trying to get a parameter value that does not exist Tracebacks
- Mention the difference between entity_byname and element_name_list in documentation HOT 2
- Support EPS Value in GDX Exporter HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spine-database-api.