The Wayback Machine - https://web.archive.org/web/20210315032005/https://github.com/topics/collaboration
Skip to content
#

collaboration

Here are 1,010 public repositories matching this topic...

mattermost-server
mkraft
mkraft commented Feb 1, 2021

Summary

The intent is that the API for the client config return values that are logically boolean as JSON values true or false rather than string values "true" or "false".

Steps to reproduce

Request the client config from the API:

curl 'https://community-daily.mattermost.com/api/v4/config/client?format=old'

Expected behavior

Values are returned

server
Dieter15
Dieter15 commented Feb 23, 2021

According to NC documentation https://docs.nextcloud.com/server/20/admin_manual/configuration_server/occ_command.html there is no OCC command for deleting / removing a calendar.

Is your feature request related to a problem? Please describe.
Feature request not related to a problem, at least not to a known problem.

Describe the solution you'd like

  1. Provide an OCC command for delet
timabbott
timabbott commented Mar 12, 2021

These are already documented on /api/start-a-call, but many folks looking for video call provider integrations are likely to look at /integrations, and it'd be very natural for them to be there.

Since they don't have a webhook-style implementation, the markdown docs implementation belongs in templates/zerver/integrations/*.md along with of course registration in zerver/lib/integrations.py

dvc
ChumpChief
ChumpChief commented Dec 14, 2020

With #4556 we now have localized eventing on subdirectories ("containedValueChanged"). We should consider using these events in our examples where we currently do path inspection on the "valueChanged" event.

Based on a quick search, looks like the following might benefit:

  • examples\data-objects\primitives\src\main.tsx
  • examples\data-objects\todo\src\TextList\TextListView.tsx
  • [
Open

[BUG]

2
mynameisvinn
mynameisvinn commented Mar 9, 2021

🐛🐛 Bug Report

⚗️ Current Behavior

Hub's version info is present in two locations, setup.py and hub/version.py. As result, the released version displays the wrong version info (1.2.3 instead of 1.3.0) when users do hub --version.

🧰 Possible Solution (optional)

Remove version info from setup.py.

Improve this page

Add a description, image, and links to the collaboration topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the collaboration topic, visit your repo's landing page and select "manage topics."

Learn more