Releases: SkygearIO/py-skygear
Releases · SkygearIO/py-skygear
v0.18.0
v0.17.0
v0.16.0
v0.15.0
v0.14.0
v0.13.1
v0.13.0
Features
- Include both api_key and access_token in send_action
- Provide meta attributes like created_by on serialized_record (SkygearIO/chat#23)
- Allow RestfulRecord subclass to provide container
- Implement serving static assets for development (#23)
- Automatically generate ID for restful record
- Enable threading in http transport
- Add function to check if a table exists in schema
- Declare and collect static assets (#21, #22)
Bug fixes
- Fix handler name with slashes in http transport (#33, oursky/py-skygear#137)
- Fix handler returning werkzeug response
Other notes
- Fix bcrypt version at 2.0.0 because build failing
- Fix onbuild image not having zmq transport installed
v0.12.0
v0.11.0
Features
- Set the container default before loading source
- Problem:
When a user want to send_action to Skygear on bootsrtap, he will try to
instantiate a SkygearContianer instance. However the skygear container
is not yet loaded the default config from environment variable. It make the
developer have to load it from the environment by themselves. - Fix:
Set the container default before attempting to load the plugin source, when
loading the plugin source. Developer got a SkygearContainer with proper
defaults.
- Problem:
- Add Public ACE support
Bug Fixes
- Raise exception with proper message if no pyzmq (#13)
- Make log level respect env SKYGEAR_LOGLEVEL
Other Notes
- Update slack notification token (SkygearIO/skygear-server#19)
- Add Github issue tempalte
v0.10.0
Features
- Make pyzmq an optional dependency (refs oursky/py-skygear#129)
- Support paging and filtering in restful index
- Implement restful resource (refs oursky/py-skygear#135)
Bug Fixes
- Update development.ini in catapi
- Change docker-compose on the catapi example
- Remove paging logic from py-skygear
- Reflect database table using SQLAlchemy